Home
Modeling software deployment
Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
Webhooks
Using the webhooks, you can send text-based responses to users in messaging platform such as MS Teams and Slack when a specific event occurs during deployment process.
Adding webhooks to process
You can add a webhook template to an application, and generic processes.

Modeling software deployment
Modeling software deployment in HCL Launch includes configuring components and component processes and adding those components to applications. Then, you use processes to deploy the components to environments.
- Components
  Components represent deployable items along with user-defined processes that operate on them, usually by deploying them.
- Resources
  A resource is a logical deployment target that typically resolves to an agent and a user-defined construct that is based on the architectural model of HCL Launch.
- Applications
  Applications are responsible for bringing together all the components that must be deployed together.
- Application environments
  An environment is a user-defined collection of resources that hosts an application.
- Application templates
  With an application template, you can save and reuse a collection of resources, environments, processes, and tagged components or component templates to create a standardized application.
- Application processes
  Application processes, like component processes, are created with the process editor. You use application processes to deploy or to roll back components.
- Application blueprints
  An application blueprint maps application components to a resource template. When you create an environment or provision one from the cloud, you can use the blueprint as a model.
- Snapshots
  A snapshot is a collection of specific versions of components and processes. Typically, a snapshot represents a set of component versions that are known to work together. In most cases, snapshots include all of the components in an application.
- Creating manual application tasks
  A manual application task interrupts an application process until manual intervention is done. To create a manual task, add a manual step to an application process and select a notification template.
- Approval process
  You can add approval requirements to deployments. Deployments with approvals cannot be completed until all approvers respond. Approvers can respond to requests on the Work Items tab, or by email.
- Inventories
  You use different inventories to track installed components and properties in HCL Launch elements.
- Processes
  Processes are automated tasks that run on agents.
- Statuses
  Create and apply statuses to track component inventory states or to track component versions in environments and resources.
- Properties
  Properties are variables that store information about many different elements, including components, environments, processes, and applications. You can also set global properties for the system.
- Tags
  A tag is a user-defined, shared, short label that you use to classify, view, and conduct operations on objects such as applications, components, agents, and resources.
- Webhooks
  Using the webhooks, you can send text-based responses to users in messaging platform such as MS Teams and Slack when a specific event occurs during deployment process.
  - Managing webhook template
    Manage a webhook template for the events your webhook will listen to and push notifications to your messaging platform.
  - Adding webhooks to process
    You can add a webhook template to an application, and generic processes.
- Secret Stores
  Allows HCL Launch to retrieve credentials of individual servers from the Vault and authenticates a plug-in step in the deployment process.

Adding webhooks to process

You can add a webhook template to an application, and generic processes.

Before you begin

Prerequisite

Before you add a webhook to application, make sure that you have created an environment for the application and have resources added to it.

Procedure

Procedure

Open the webhook configuration UI using any of the below methods:
- To add webhook to an application, go to Applications > application name > Configuration > Webhooks > Add Webhook.
- To add webhook to a process, go to Processes > process name > Configuration > Webhooks > Add Webhook.
The Add Webhook window is displayed.
Copy the generated webhook URL and paste it in the URL field.
Refer to the How-tos section for information about how you can get this URL.
Specify an Event Type.
Select a template name from the Webhook Template field.
See Managing webhook template for more information.
If you are adding the webhook to an application, specify the environment name from the Environments field.
Submit your changes.

Results

The webhook template is added to the application. In the event when a process runs, the notifications will appear in your configured messaging platform app.

Note:

Notifications can be out-of-order in few of the cases. One of the case can be when:
1. Message A is sent and fails to complete for a reason, for example, the remote server has an error.
2. Message B is sent and completes.
3. The remote server error is now resolved.
4. The message A is resent, and completes.
When you export or import an application or a generic process, the webhooks are also imported/exported with them.